[NO-TICKET] Bump version to 0.2.11#37
Merged
Merged
Conversation
|
Large mixed-version bump and runtime-protect feature adds significant complexity. 🎯 Quality: 60% Average · 📦 Size: Large — consider splitting if possible 🛡️ Standards: no pre-flight fit check ran for this change — wire 📈 This month: Your 215th PR — above team average · Averaging Good |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ejntaylor
force-pushed
the
elliot/bump-0.2.11
branch
from
e76fa3e to
1b97f0e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One-line release bump on top of #36 (protect command landing on main). Also syncs the long-stale package-lock.json version fields (they still said 0.2.8 even in the published 0.2.10).
0.2.11 = everything on npm 0.2.10 (protect command) + #35 (build-stack descriptor in mark-build).
After this merges, the stale v0.2.11 tag/release will be recreated on the merge commit so the publish workflow's version guard passes.
🤖 Generated with Claude Code